Bus converter

ABSTRACT

A device for coupling a fieldbus to a local bus for connection to at least one data bus subscriber, the device comprising a first unit that is connectable to the fieldbus and is adapted for sending and receiving data via the fieldbus; a second unit that is connectable to the local bus and is adapted for sending and receiving data via the local bus in at least one data packet; a data management unit that is connected to the first unit and the second unit, wherein the data management unit is adapted for transferring first symbols from data received via said first unit to said second unit in a sequence-dependent manner; and wherein the second unit is adapted to send at least one data packet including the first symbols on the local bus. In addition, a corresponding method for transferring data is described.

This nonprovisional application is a continuation of U.S. applicationSer. No. 16/694,432, which was filed on Nov. 25, 2019, which is acontinuation of International Application No. PCT/EP2018/062971, whichwas filed on May 17, 2018, and which claims priority to German PatentApplication No. 10 2017 208 824.9, which was filed in Germany on May 24,2017, and which are all herein incorporated by reference.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates to a device for connecting a fieldbus to alocal bus and in particular to a bus converter for converting data froma data stream of a fieldbus to a data stream of a local bus.

Description of the Background Art

Devices for connecting two bus systems are typically used in automationsystems.

Automation systems are used in particular for controlling industrialplants, buildings and means of transport. Usually, a plurality ofsensors and actuators are required in order to control an automationsystem. These sensors and actuators monitor and control the process thatthe system carries out. These different sensors and actuators of anautomation system are often referred to as automation devices.

These automation devices may either be connected directly to acontroller of the automation system or may first be connected to inputand output modules, often referred to as I/O modules. These may in turnbe connected directly to the controller. These automation devices mayeither be integrated directly into the I/O modules or may be connectedto them via a wired or wireless connection.

The control of an automation system is usually accomplished using one ormore programmable logic controllers (PLCs). The PLCs may be arrangedhierarchically or decentrally in an automation system. There aredifferent performance classes for the PLCs, so that they may be subjectto different controls and rules depending on the computing and memorycapacity. In the simplest case, a PLC has inputs, outputs, an operatingsystem (firmware) and an interface via which a user program may beloaded.

The user program determines how the outputs are switched as a functionof the inputs. The inputs and outputs may be connected to the automationdevices and/or the I/O modules, and the logic stored in the user programmay be used to monitor or control the process that the automation systemperforms. The sensors provide monitoring of the process, and theactuators provide control of the process. The controller may also bereferred to as a central controller or central unit and controls atleast one automation device or I/O module connected to the controller.

However, it is very laborious to directly connect the automation deviceswith at least one control system or to connect the I/O modules with theat least one control system in the form of a parallel wiring, i.e.,running a line from each automation device or each I/O module to thehigher-level control system. Especially with the increasing degree ofautomation of an automation system, the cabling effort increases in thecase of parallel wiring. This involves a great deal of effort in projectplanning, installation, commissioning and maintenance.

For this reason, typically in contemporary automation technology, bussystems are used that allow connecting the automation devices or the I/Omodules to the control system. Such subscribers of a bus system are alsoreferred to as bus subscribers. Because data is exchanged on the bussystem, the bus subscribers are often also called data bus subscribers.In order to further simplify the connection of the individual automationdevices or I/O modules with the bus system, currently, individual groupsof automation devices or I/O modules are often first connected to oneanother to form a local bus system using a specialized local bus, andthen at least one subscriber of this local bus is connected to the bussystem that is connected to the control system. In this case, the localbus system may differ from the bus system that is used to establish theconnection with the control system.

In a group of local bus subscribers, the subscriber that is connected tothe bus system of the control system is often referred to as a local busmaster. Alternatively, the term “head-end station” of the local bussystem is also used. In contrast to the other local bus subscribers,this local bus master may contain additional logics, circuits orfunctionalities that are necessary for connecting to the bus system ofthe control system. The local bus master itself may also contain a PLC.This subscriber may also have logics and circuits for conversion betweenthe two bus systems. The local bus master accordingly may also bedesigned as a gateway or bus converter, and ensures that the dataavailable in the format of one bus system is converted into the formatof the local bus system and vice versa. Usually, but not necessarily,the local bus master is specialized for connecting the local bus to thehigher-level bus.

The local buses that are used are usually adapted to the special usagerequirements of the automation devices or I/O modules, or take intoaccount the specific hardware design thereof. In this case, the groupsof automation devices or I/O modules of the local bus system usuallyform a subgroup of the automation system for executing a specific taskin the process that the automation system carries out. The dataexchanged on the buses for the process is often referred to as local busdata or process data, because this data contains information forregulating or controlling the process that the automation system carriesout. This data may comprise, among other things, measurement data,control data, status data and/or other information. Depending on the busprotocol used, this data may be prepended (“header”) or appended(“tail”) to other data. This other data may contain informationregarding the data, or information regarding internal communication onthe local bus. In this case, a multiplicity of different information isknown that may be prepended or appended to the data depending on the busprotocol used. The local bus subscribers connected to a local bus mayalso be referred to as data bus subscribers because they exchange dataon the local bus. A data bus subscriber in this case is used to controlor monitor a process, in particular by outputting control signals, forexample to actuators, and/or by receiving measurement signals, forexample from sensors.

The data bus subscriber converts the control signals and/or measurementsignals into data for the local bus or vice versa.

A ring bus is a specialized form of a local bus, as is known for examplefrom U.S. Pat. No. 5,472,347 A. In a ring bus, the data bus subscribers,for example the automation devices or I/O modules, are each respectivelyconnected to their directly adjacent data bus subscribers, and data isforwarded in sequence from one data bus subscriber to another. The datatransmitted on the local bus may also be referred to as local bus data.This means that the data is not sent to all data bus subscriberssimultaneously, but in sequence, with a data bus subscriber receivingdata from its upstream data bus subscriber and forwarding data to itsdownstream data bus subscriber. Between receiving the data andforwarding it, the data bus subscriber may process the received data.When the data has reached the last data bus subscriber in the sequence,the data from the last data bus subscriber is returned back to the firstdata bus subscriber. The return may take place via all data bussubscribers or by bypassing them via a bypass line. The ring bus thushas a downstream flow and an upstream flow of data. The data in a ringbus is usually transmitted in the form of data packets that pass throughall data bus subscribers.

In a ring bus, a data packet is passed from one data bus subscriber toanother. At any given time, a data bus subscriber receives only part ofthe data packet from its upstream data bus subscriber. When the data bussubscriber has processed the data contained in this part, the part isforwarded to the downstream data bus subscriber and at the same time anew part of the data packet is received from the upstream data bussubscriber. In this way, all parts of the data packet pass sequentiallythrough all data bus subscribers.

In the known ring bus systems or other local bus systems, bus convertersare used that convert the data streams from the control system into alocal bus-compliant format.

Usually, high-performance controllers are used that sort the dataoriginating from the control system in such a way that this data isavailable in a local bus-compliant format, corresponding to the sequenceof the data bus subscribers on the local bus. In other words, thesequence of the data after sorting corresponds to the sequence in whichthe data bus subscribers are arranged on the local bus. This sortingmakes addressing unnecessary in such bus systems, because the data isarranged according to the physical position of the data bus subscribersin the local bus. For example, the data directed to the first data bussubscriber is set to the first position in the local bus-compliantformat, the data directed to the second data bus subscriber in the localbus is set to the second position in the local bus-compliant format, andso forth. To ensure that this conversion and in particular the sortingtakes place without major delays, in known systems high-performance,high-clocked controllers are usually used. But even with thesehigh-performance controllers, a delay may only be minimized to a certaindegree.

High-performance controllers also have various drawbacks; thecontrollers usually have to be actively cooled, have a high powerconsumption and are expensive.

SUMMARY OF THE INVENTION

It is therefore an object of the present invention to provide a deviceand a corresponding method with which the conversion of data from afieldbus to a local bus and in particular to a ring bus may be carriedout almost without delay and the conversion does not require complexhardware.

The device according to an exemplary embodiment of the invention, whichmay also be referred to as a bus converter or gateway, has a first unitthat is connectable to a fieldbus and is adapted for sending andreceiving data via the fieldbus. A fieldbus may be any bus that may beused in an automation system and that may be used to establish aconnection to the control system, for example the PLC.

The connection to the control system may also be established via severaldifferent fieldbuses; the entire connection between the first unitaccording to the invention and the control system should be understoodas a single fieldbus, even if this connection is formed of a pluralityof different fieldbuses. The first unit according to the invention isadapted to be connected to the fieldbus. For this purpose, the firstunit may have an interface that is designed for the fieldbus. Theinterface may establish a wired or wireless connection with thefieldbus. A data stream may be received from the fieldbus, and a datastream may be output to the fieldbus, via the interface of the firstunit or via the first unit. The first unit may also be called a fieldbuscore (FBC) due to its connectivity to the fieldbus. The FBC may bedesigned as an individual arithmetic logic unit, as a computing core, oras a computing circuit that is designed as a digital logic circuit thatin particular is designed as at least a part of a semiconductor chip.The FBC may be implemented for example in an application-specificintegrated circuit (ASIC) or in a field programmable gate array (FPGA),or in another programmable logic device (PLD), or a discrete gate ortransistor logic.

Additionally, the device according to the invention also has a secondunit that is connectable to a local bus, in particular a ring bus, andis adapted for sending and receiving data via the local bus in the formof at least one data packet. The data packets may also be referred to asdata telegrams. For example, a data packet has a header, a payload, andadvantageously, a checksum. A data packet is advantageously acommunication data packet or a process data packet.

A communication data packet does not contain any process data.Advantageously, a communication data packet contains data in particularfor programming and/or for controlling and/or for monitoring and/or foridentifying at least one data bus subscriber. Advantageously, thecommunication data packet has an address that is mapped to at least onedata bus subscriber. Preferably, the data bus subscriber is designed toevaluate the address.

A process data packet comprises process data that are sent and/orreceived by the data bus subscribers of the local bus. Advantageously,the process data packet does not have an address for transmitting theprocess data to or from a data bus subscriber in the local bus. In theprocess data packet, for example, the process data is arranged in such away that data bus subscribers may recognize the process data associatedwith the respective data bus subscriber based on the respective positionof the process data in the process data packet, for example one or morebits within an associated contiguous data block (1 byte).Advantageously, the process data packet has an identifier (IDE) that ismapped to the type of data packet, i.e., the process data packet, andthat the data bus subscriber is able to identify. The process data mayalso be referred to as local bus data.

The protocols used on the fieldbus and the local bus may differ, so thatthe fieldbus-compliant format cannot be sent without being converted forthe local bus, and conversely the local bus-compliant format cannot besent without being converted for the fieldbus.

The second unit, according to the invention, is adapted to be connectedto the local bus. For this purpose, the second unit may have aninterface that is designed for the local bus. The interface mayestablish a wired or wireless connection with the local bus. A datapacket may be sent on the local bus, and a data packet may be receivedfrom the local bus, via the interface of the second unit or via thesecond unit. The second unit may also be called a local bus core (LBC)due to its connectivity to the local bus. The LBC may be designed as anindividual arithmetic logic unit, as a computing core, or as a computingcircuit that is designed as a digital logic circuit that in particularis designed as at least a part of a semiconductor chip. The LBC may beimplemented in an ASIC, or in an FPGA, or in another PLD, or in adiscrete gate or transistor logic.

The device according to the invention also comprises a data managementunit that is connected to the first and second units. The datamanagement unit may also be referred to as the management unit (MU), inwhich case it may be referred to as the fieldbus management unit (FMU)or local bus management unit (LMU) according to the direction in whichit functions.

The connection may advantageously be a parallel bus between the units,that for example is designed as a 32-bit parallel bus. The datamanagement unit is adapted for sequence-dependently transferring firstsymbols, from data received via the first unit (FBC), to the second unit(LBC). Sequence-dependent in this context means that symbols aretransferred to the second unit according to the sequence in which theywere received from the first unit. The sequence accordingly conforms tothe incoming symbols. For example, the symbols received via the fieldbusmay be transferred to the second unit in a correct sequence. Forexample, the sequence of the symbols received via the fieldbus isunchanged or is predominantly unchanged, i.e., the symbols are alsotransferred to the second unit in the order in which they are receivedon the fieldbus. Thus, there is no sorting, because the sequence of thesymbols is maintained. The symbols may be said to be transferredone-to-one. The transferred symbols may be process data received fromthe control system via the fieldbus in a fieldbus-compliant format. Thefieldbus-compliant format may comprise process data as well as otherdata that is prepended to, appended to, or superimposed on, the processdata. For example, the other data may be bus-specific and the processdata may be bus-neutral. In a fieldbus-compliant format, other data,which may be referred to as the header, and which is usually used forpurposes of addressing and control, is usually prepended to the processdata. Other data may also be appended to the process data, which may beused for error detection. The process data is a component of the payloadpart of the fieldbus-compliant format. The process data are designed tocause a control, regulation or other reaction by the data bussubscribers of the local bus. For example, fieldbus telegrams may bereceived via the fieldbus in which the process data is contained in theform of symbols with a fixed number of bits and in which the symbols arearranged in a first sequence in the fieldbus telegram.

The data management unit may be adapted to transfer the symbols from thefieldbus telegram to the LBC in a second sequence. Preferably, the firstand second sequences of the symbols coincide. The data management unitmay be adapted to transfer only the process data. In other words, thedata management unit or the first unit may be adapted to select theprocess data from the fieldbus-compliant format or the fieldbustelegram. The data management unit may be designed as an individualarithmetic logic unit, as a computing core, or as a computing circuitthat is designed as a digital logic circuit that in particular isdesigned as at least a part of a semiconductor chip. The data managementunit may be implemented in an ASIC, or in an FPGA, or in another PLD, orin a discrete gate or transistor logic. The FBC, the LBC and the datamanagement unit may also be implemented together in an ASIC, or in anFPGA, or in a PLD, or in a discrete gate or transistor logic.Particularly after the transfer, the local bus master may use amanipulation unit to modify the process data in a targeted manner. Forthis purpose, the local bus master advantageously comprises instructionsthat effect a modification of the process data.

After the first symbols have been transferred to the LBC and a datapacket has been generated that carries the transferred symbols, thisdata packet may be sent on the local bus for example in parts of 8 bits,i.e., 1 byte, and the individual parts of the data packet may passsuccessively through the data bus subscribers of the local bus. Thus, atany given time, a data bus subscriber receives only a part of the datapacket from its upstream data bus subscriber. When the data bussubscriber has processed the process data contained in this part, thepart is forwarded to the downstream data bus subscriber, and at the sametime, a new part of the data packet is received from the upstream databus subscriber. The LBC and the data bus subscribers of the local busmay be clock-synchronous, so that when the LBC sends a new part of thedata packet on the local bus, the respective data bus subscribers alsosend the currently-available part of the data packet to their respectivedownstream data bus subscriber. The last data bus subscriber in thelocal bus may send the part currently available to it back to the LBC,either again through all data bus subscribers or via a bypass line. TheLBC in this case may be synchronized to the clock of the fieldbus, i.e.,to the clock in which the FBC receives fieldbus telegrams from thefieldbus.

The LBC may be adapted in this case to output the start of the datapacket on the local bus before the first symbols have been receivedcompletely via the FBC.

The device according to the invention enables an accelerated conversionof a data stream from a fieldbus to a local bus and vice versa throughthe sequence-dependent transfer of process data. The conversion of allprocess data necessary for the data bus subscribers of the local busthus occurs in a bus-neutral fashion and with minimal delay and minimaljitter. Because the conversion is always sequence-dependent, it isadvantageous that the data bus subscribers know about the sequence used;the sequence may deviate from the sequence of the physical positions ofthe data bus subscribers in the local bus. Knowledge of the sequenceallows the data bus subscribers to be programmed in such a way that theymay extract the process data directed to them from the data packetwithout having to sort the process data in order to do so. Theprogramming of the data bus subscribers may take place, for example,with a communication data packet that the second unit sends before thedata packet that carries the process data.

The data management unit can be adapted to prepend and/or append and/orinterpolate additional symbols into the first symbols. It is conceivablethat the other symbols are blank symbols that are used to monitor theintegrity on the local bus, for example if the local bus does not allowany gaps in the symbols or if the LBC expects a certain number ofsymbols but this number does not correspond to the number of the firstsymbols. The data management unit may also be adapted to interpolateadditional symbols into the first symbols. The data management unit mayalso be adapted to remove unneeded symbols from the first symbols.

The data management unit can temporarily store the first symbols. Forexample, the data management unit may temporarily store the transferredsymbols in a memory to make them available to a controller forevaluation.

In this case, the controller is not set up to transfer data between theFBC and the LBC. Temporary storage makes it possible, for example, tocheck the transferred symbols without interrupting the data streams.Moreover, temporary storage also enables a delta comparison of symbolsto be carried out before they are sent on the local bus and after theyare received from the local bus. For the temporary storage of thetransferred symbols, the device according to the invention may have atleast one volatile or non-volatile memory, for example a pseudo staticdynamic random access memory. The skilled person understands, however,that any other component for storing data may also be used for temporarystorage. This component need not itself be part of the device, but maybe maintained externally from it, or may be an additional module. Thedevice and in particular the data management unit need only have accessto the component, for example, a memory.

The LBC is adapted to generate a data packet that comprises the firstsymbols, and to send the data packet on the local bus. The data packetmay be sent on the local bus in symbol form. The LBC may make allnecessary protocol-specific adjustments in order to send the data packeton the local bus. The LBC is additionally adapted to receive a datapacket from the local bus; the received data packet may contain secondsymbols that differ from the first symbols. The LBC is also adapted tomanipulate the first and/or second symbols. This manipulation may bebitwise and may be used to adjust the first and second symbols accordingto the respective direction of transmission.

The data management unit can function as a master unit. The datamanagement unit has a first master interface connected to a slaveinterface of the FBC, and the data management unit has a second masterinterface connected to a slave interface of the LBC. This means that thedata management unit controls the process of transferring the firstsymbols between the FBC and the LBC by requesting symbols from the FBCvia the first master interface and transferring the requested symbols tothe LBC via the second master interface.

The data management unit can comprise a first data transfer unit, DTU0;DTU0 is adapted to read the first symbols from a buffer of the FBC viathe first master interface based on first instructions and to write theminto a buffer of the LBC via the second master interface. DTU0 isadditionally adapted to send the validity of the written first symbolsto the LBC via the second master interface. The validity is indicated,for example, by a control signal, an identifier, a flag, or anothercode. Only when the validity is indicated are the first symbols sentfrom the LBC on the local bus. If there is no determination of validity,then for example the first symbols last received as valid may betransferred and sent again. Alternatively, in this case, default symbolsor blank symbols may also be sent, which bring about either no or adefined control, regulation, or the like by the data bus subscribers.This prevents incorrectly-transferred first symbols from being sent onthe local bus, which could lead to incorrect control, regulation, etc.of the data bus subscribers or the actuators connected to them. The datamanagement unit may also comprise a second data transfer unit, DTU₁,which is adapted to read second symbols from an LBC buffer via thesecond master interface based on second instructions, and to writesecond symbols to an FBC buffer via the first master interface. DTU0 isaccordingly adapted to transfer symbols from the fieldbus to the localbus, while DTU₁ is adapted to transfer symbols from the local bus to thefieldbus. DTUs 0 and 1 are preferably implemented as separate hardware,so that there is a separation between the transfer directions; thehardware separation may allow parallel processing in both transferdirections, i.e. a simultaneous transfer in both directions may beguaranteed. The DTU₁ may be additionally adapted to write a part of thesecond symbols into the buffer of the FBC only if the LBC sends thevalidation of the second symbols. This has the advantage that sendingthe second symbols to the control system via the fieldbus may be delayeduntil the validity of the second symbols has been checked. The reasonfor this is that the FBC only sends the second symbols from the buffervia the fieldbus when they are complete, for example when the buffer hasfilled to a certain extent, thus for example when the fieldbus telegramis complete. Additionally, the data management unit may also be adaptedto transfer the second symbols based on a control signal of the LBC.

Only when this control signal is present are the second symbolstransferred.

The first and second data transfer units DTU_(0,1) may also be referredto as copy units. DTU₀ copies process data—selected from a datastream—that has been received into the buffer of the LBC via thefieldbus. DTU₁ copies process data—selected from a data stream—that wasreceived via the local bus into the buffer of the FBC. The FBC and LBCthen each send their respective buffer contents to the fieldbus or localbus. The FBC and LBC do not operate bus-neutrally in this case, becausethey pack the corresponding buffer contents into a fieldbus- or localbus-compliant format. Thus, the FBC and the LBC are adapted to therespective bus systems. These units may therefore be designed to bereplaceable so that they may be changed according to the bus systemsused. However, the copy units are bus-neutral because they only copy theprocess data without taking other bus-specific information into account.The copy units copy the first and second process datasequence-dependently. This means that the copy units copy the processdata in the same sequence in which it is taken from the data streams.This means, for example, that the first process data are copied into theLBC in the sequence in which they were received via the fieldbus. Inreverse sequence, this means that the second process data is copied tothe FBC in the sequence in which it was received via the local bus.Thus, the copy units copy the process data between the FBC and the LBCwithout changing the sequence of the data.

In an exemplary embodiment of the device according to the invention, thedevice further comprises a computing unit for controlling the FBC and/orthe data management unit and/or the LBC and for evaluating the first andsecond symbols. The computing unit may be a microcontroller connected tothe FBC, the LBC and/or the data management unit via a parallel bus. Forexample, the bus may be a 32-bit parallel bus.

The computing unit may be adapted to program and modify the instructionsaccording to which the FBC, LBC, and/or data management unit operate. Inaddition, the computing unit may be adapted to receive data from thedata management unit via the fieldbus or from the local bus and to readand evaluate it. Additionally, the computing unit may be adapted to readand evaluate the first symbols that the data management unit has storedtemporarily, i.e., the buffered process data. The computing unit mayalso be adapted to control the LBC, in particular to write control datato the LBC for manipulating the process data.

The first unit can be adapted to check the validity of the data receivedvia the fieldbus. The first unit may also be adapted to signal thevalidity of the received data. The second unit may be adapted to checkthe validity of the data received via the local bus. The second unit mayalso be adapted to signal the validity of the received data. Forexample, data may only be transferred if a corresponding validation hasbeen signaled. The data streams may be validated, for example, using CRCchecks. Both or only one unit may be adapted to check the correspondingvalidity. The first and second units may be adapted not to output datato the fieldbus or local bus if the respective other unit does notsignal that the transferred data or received data is valid. It mayhappen that the fieldbus connected to the first unit requires acontinuous transmission of data, i.e., sending data without timeinterruption, in which case the last data recognized as valid by thefirst unit may be sent on the fieldbus if the validity of the presentdata is not otherwise indicated.

The device can also have a clock and/or timer for generating an internaltiming and/or for transmitting it to the data bus subscribers of thelocal bus. Moreover, the device according to the invention may have asynchronization unit for synchronizing the clock and/or timer to theclock of the fieldbus. For example, the synchronization unit may beadapted to detect transitions in the data streams received from thefieldbus and may use them to control the clock frequency of the internalclock signal and to set a defined phase relationship of the internalclock signal to the detected transitions.

The timer of the device according to the invention may thus besynchronized, for example, with a timer that the control system uses.The device according to the invention may also transmit this timing tothe data bus subscribers of the local bus. This timing may be used whensending parts of the data packet on the local bus.

The fieldbus can be ARCNET, AS-Interface, BACNet, BITBUS, ControlNet,Profibus/Profinet, EtherCAT, Ethernet/IP, Interbus, AS-Interface, CIPprotocols, CANopen, CC-Link, Modbus, Modbus/TCP, P-NET, Lonworks,SERCOS, BACnet, Bitbus, Measurement Bus, Powerlink, DeviceNet, RTPS,DALI, EIB, FAIS-Bus, FIB-Bus, FlexRAY, HART, KNX, LCN, LIN, LON, P-Net,T-Bus, or VARAN. However, it is also conceivable that the fieldbus mayuse a different bus protocol. The protocol that the fieldbus uses mustonly allow the process data to be unambiguously distinguished from thenon-process data, i.e. the other data contained in the data stream. Forthis purpose, for example, the protocol must unambiguously predeterminethe position of process data in the data stream and the position ofnon-process data. Alternatively or additionally, if the process data isnot always at the same position in the data stream, the protocol mustmake it possible to determine the position of the process data usingother information in the data stream. It is necessary to determine theposition of the process data in the data stream so that the process datamay be selected from the data stream.

The first unit can be designed as a first logic circuit and the secondunit can be designed as a second logic circuit. These first and secondlogic units are adapted to be operated independently of one another.Thus, the two logic circuits may perform different computationaloperations at the same time. This is achieved by a separate hardwareimplementation of the first and second logic circuits.

The first unit can be adapted to receive a serial data stream from thefieldbus and output a serial data stream on the fieldbus. The secondunit is adapted to output a serial data stream on the local bus andreceive a serial data stream from the local bus. The first and secondunits are preferably adapted to convert the serial data stream into aparallel data stream. The first and second units are preferablyconnected to the data management unit via a respective parallel bus.These parallel buses may be designed as 32-bit parallel buses. Thus, inthe device according to the invention, the symbols of the respectivedata streams are forwarded in parallel. The respective parallel busesmay also be sections of a single parallel bus.

The above-mentioned object is also accomplished by a method fortransferring data between a fieldbus and a local bus, in particular aring bus, with at least one data bus subscriber being connected to thelocal bus. The method according to the invention comprises receivingdata over the fieldbus at a first unit, the received data containingfirst symbols; transferring the first symbols in a sequence-dependentmanner to a second unit; and sending a data packet containing the firstsymbols on the local bus from the second unit.

Further scope of applicability of the present invention will becomeapparent from the detailed description given hereinafter. However, itshould be understood that the detailed description and specificexamples, while indicating preferred embodiments of the invention, aregiven by way of illustration only, since various changes, combinations,and modifications within the spirit and scope of the invention willbecome apparent to those skilled in the art from this detaileddescription.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will become more fully understood from thedetailed description given hereinbelow and the accompanying drawingswhich are given by way of illustration only, and thus, are not limitiveof the present invention, and wherein:

FIG. 1 is a schematic block diagram of an exemplary automation systemwith a programmable logic controller, a fieldbus, an exemplaryembodiment of the device according to the invention, and an exemplaryring bus;

FIG. 2 is a schematic block diagram of an exemplary embodiment of thedevice according to the invention;

FIG. 3 a is a schematic block diagram of an exemplary embodiment of thedevice according to the invention, having first symbols transferred fromthe fieldbus to the ring bus; and

FIG. 3 b is a schematic block diagram of an exemplary embodiment of thedevice according to the invention with second symbols transferred fromthe ring bus to the fieldbus.

DETAILED DESCRIPTION

FIG. 1 shows a schematic block diagram of an automation system. Theskilled person understands that the automation system shown is onlyexemplary, and that all elements, modules, components, subscribers andunits belonging to the automation system may be designed differently butmay still fulfil the basic functionalities described herein.

The automation system shown in FIG. 1 has a higher-level controller 1,which may be implemented, for example, using a programmable logiccontroller (PLC). A PLC 1 of this type is basically used to control andregulate the process that the automation system carries out. Currently,however, PLCs 1 used in automation systems also perform more extensivefunctions, such as for example visualization, alarming and recording alldata relating to the process; as such, the PLC 1 functions as ahuman-machine interface. There are PLCs 1 in different performanceclasses that have different resources (computing capacity, memorycapacity, number and type of inputs and outputs, and interfaces) thatenable the PLC 1 to control and regulate the process of the automationsystem. A PLC 1 usually has a modular structure and formed of individualcomponents, each of which fulfils a respectively different task. A PLC 1usually formed of a central computer assembly (with one or more mainprocessors and memory modules) and a plurality of assemblies with inputsand outputs.

Such modularly-structured PLCs 1 may readily be extended by addingassemblies. In this case, which assemblies must be integrated into thePLC 1 will depend on the complexity of the process and the complexity ofthe structure of the automation system. In contemporary automationsystems, the PLC 1 is usually no longer an independent system; instead,the PLC 1 is connected to an internet or intranet via correspondinginterfaces. As a result, the PLC 1 is part of a network via or fromwhich the PLC 1 may receive information, instructions, programming andthe like. For example, the PLC 1 may receive information about materialssupplied to the process via a connection to a computer located in anintranet or internet, so that, for example, the process may be optimallycontrolled by knowing the number or nature thereof. It is alsoconceivable that a user may control the PLC 1 by accessing it from anintranet or internet. For example, a user may use a computer, also knownas a host computer, to access the PLC 1 and check, change or correct thePLC's user programming. Accordingly, the PLC 1 may be accessed from oneor more remote maintenance or control stations. The host computers mayhave visualization devices for representing process workflows.

To control the process of the automation system, the PLC 1 is connectedto automation devices. Bus systems are used for these connections tominimize wiring effort. In the exemplary embodiment shown in FIG. 1 ,the PLC 1 is connected to a local bus master 3 of a lower-level localbus system via a higher-level bus 2, which in the exemplary embodimentshown here may be a fieldbus. However, not only a local bus master 3 ofa local bus as in the exemplary embodiment shown here, but also anyother subscribers that are designed to communicate with the PLC 1, maybe connected to the higher-level bus 2.

In the exemplary embodiment shown here, the higher-level bus 2 isconnected to the local bus master 3. To this end, the local bus master 3has a first interface 4 that is designed in such a way that it may beconnected to the higher-level bus 2.

For this purpose, the interface 4 may, for example, have a receptacle inthe form of a socket, and the higher-level bus 2 may have a plug thatthe socket may accommodate. For example, the plug and socket may be amodular plug and modular socket, with each core of the higher-level bus2 being electrically or optically connected to a connection in themodular socket. However, the skilled person is also familiar with otheroptions for designing an interface 4 so that the local bus master 3 maybe electrically or optically connected to the higher-level bus 2. Theskilled person is familiar with screw, bearing, click or plugconnections that may be used to establish an electrical or opticalconnection. A male plug is usually accommodated by a female counterpart.This accommodation usually not only establishes the electrical oroptical connection, but also ensures that the two parts are mechanicallycoupled and may only be separated from one another by applying a certainforce. However, it is also possible that the higher-level bus 2 may bepermanently wired to the interface 4.

The local bus master 3 in the exemplary embodiment shown here has anadditional second interface to connect the local bus master 3 to thelocal bus. Data bus subscribers 7 a, 7 b, . . . , 7 n are connected toor form the local bus. The local bus is advantageously designed in sucha way that a data packet sent by the local bus master 3 is transmittedback to the local bus master 3 by all the data bus subscribers 7 a, 7 b,. . . , 7 n connected to the local bus. In this case, a data bussubscriber 7 a, 7 b, . . . , 7 n always receives only a part of the datapacket the data bus subscriber 7 a, 7 b, . . . , 7 n upstream of it.After a time period in which the data bus subscriber 7 a, 7 b, . . . , 7n may process the data contained in this part, it forwards the part tothe downstream data bus subscriber 7 a, 7 b, . . . , 7 n, and at thesame time receives a new part of the data packet from the upstream databus subscriber 7 a, 7 b, . . . , 7 n. In this way, all parts of the datapacket pass sequentially through all the data bus subscribers 7 a, 7 b,. . . , 7 n. The local bus is advantageously designed with a ring-shapedstructure. Such local buses may also be referred to as ring buses 6. Thelocal bus may alternatively be designed to be stranded or star-shaped,or to have a combination or mixture of the above designs. In this case,the data packets are sent and received via the second interface of thelocal bus master 3.

In the exemplary embodiment shown here, the second interface is dividedinto a first part 5 a and a second part 5 b. The first part 5 a of thesecond interface establishes the downstream connection in the ring bus 6and the second part 5 b of the second interface establishes the upstreamconnection in the ring bus 6.

In the exemplary embodiment shown here, the ring bus 6, the datatransmission direction of which is shown with arrows in the exemplaryembodiment of FIG. 1 , has data bus subscribers 7 a, 7 b, . . . , 7 n.In the exemplary embodiment shown here, these data bus subscribers 7 a,7 b, . . . , 7 n each have a respective interface 8 in order to receivedata from an upstream or preceding data bus subscriber 7 a, 7 b, . . . ,7 n. Data bus subscriber 7 a receives data from the upstream local busmaster 3 via the interface 8. In addition, in the exemplary embodimentshown here, the data bus subscribers 7 a, 7 b, . . . , 7 n eachrespectively have an interface 9 in order to forward data to adownstream or subsequent data bus subscriber 7 a, 7 b, . . . , 7 n. Databus subscriber 7 a sends data to the downstream data bus subscriber 7 bvia the interface 9. The interfaces 8 and 9 are used to propagate datain the downstream direction of the ring bus 6, i.e. away from the localbus master 3. Moreover, in this exemplary embodiment the data bussubscribers 7 a, 7 b, . . . , 7 n also have interfaces 10 and 11 forpropagating data in the upstream direction of the ring bus 6, i.e.toward the local bus master 3. In the case of the data bus subscriber 7a, the interface 10 is designed to receive data from the downstream orsubsequent data bus subscriber 7 b, and the interface 11 is designed toforward data to the upstream or preceding data bus subscriber, in thiscase the local bus master 3. Thus, it may also be said that theinterfaces 9 and 11 are transmitter interfaces, while the interfaces 8and 10 are receiver interfaces.

In the exemplary embodiment shown here, the connections of theinterfaces and the PLC 1 or the data bus subscribers 7 a, 7 b, . . . , 7n are implemented with the aid of cables or printed circuit boards bydirect or indirect contacting using electrical contacts. Anotheralternative is that the individual connections are establishedwirelessly and the interfaces provide the necessary conversions for theradio standards used.

Although in the exemplary embodiment shown here, the local bus master 3and the individual data bus subscribers 7 a, 7 b, . . . , 7 n are shownspaced apart from one another, i.e. the local bus master 3 is arrangeddecentrally from the data bus subscribers 7 a, 7 b, . . . , 7 n, theskilled person understands that the data bus subscribers 7 a, 7 b, . . ., 7 n and the local bus master 3—which also represents a data bussubscriber of the ring bus 6—may also be directly connected together. Inthis case, for example, contacts of one data bus subscriber may accesscorresponding receptacles or receiving contacts of a directly adjacentdata bus subscriber in order to establish an electrical connectionbetween the data bus subscribers so that data may be sent in thedownstream and upstream directions. For example, the data bussubscribers 7 a, 7 b, . . . , 7 n may have receptacles on the sidefacing away from the master and contacts on the side facing toward themaster. If the data bus subscribers 7 a, 7 b, . . . , 7 n are thenconnected in sequence accordingly, the contacts of the one data bussubscriber 7 a, 7 b, . . . , 7 n each engage in the respectivereceptacles of the other data bus subscriber 7 a, 7 b, . . . , 7 n andan electrical connection may be established. The local bus master 3 inthis case correspondingly has contacts on the side that engage with thereceptacles of the first data bus subscriber 7 a in order to establishan electrical connection between the interfaces 5 a and 8 or theinterfaces 5 b and 11. However, the skilled person is also familiar withother possibilities for establishing an electrical or optical connectionbetween two data bus subscribers 7 a, 7 b, . . . , 7 n arranged directlynext to one another, for example pressure contacts and knife and forkcontacts.

If it is desired that the data bus subscribers 7 a, 7 b, . . . , 7 n andthe local bus master 3 are directly connected together, they may alsohave mechanical mountings or mechanical fasteners using which theindividual data bus subscribers 7 a, 7 b, . . . , 7 n and the local busmaster 3 may be connected to one another. For example, a data bussubscriber 7 a, 7 b, . . . , 7 n may have a projection on one side andan undercut on the other.

If the data bus subscribers 7 a, 7 b, . . . , 7 n are then connected insequence, a projection engages in an undercut of the other data bussubscriber 7 a, 7 b, . . . , 7 n, so that a mechanical coupling occurs.For straightforwardly sequentially arranging the data bus subscribers 7a, 7 b, . . . , 7 n, they may also be arranged on a shared mounting, forexample a top-hat rail. The data bus subscribers 7 a, 7 b, . . . , 7 nmay have appropriate fasteners for fastening onto the top-hat rail.Alternatively or additionally, the data bus subscribers 7 a, 7 b, . . ., 7 n may also, for example, have detachably connectable fasteners withwhich the data bus subscribers 7 a, 7 b, . . . , 7 n may be fastenedeither to the top-hat rail or to another mounting. For this purpose, thedetachably connectable fasteners may be replaceable and a correspondingfastener for the desired mounting may be connected to the data bussubscribers 7 a, 7 b, . . . , 7 n so that these may be fastened to thedesired mounting.

In addition, the data bus subscribers 7 a, 7 b, . . . , 7 n in theexemplary embodiment shown in FIG. 1 also have a processing unit 12.This processing unit 12 may be an arithmetic-logic unit or another typeof computing unit that may be used to process data. The processing unit12 is preferably an integral part of the data bus subscriber 7 a, 7 b, .. . , 7 n, in order to ensure particularly rapid and time-synchronizedprocessing of the data.

The processing unit 12 may also be described as the complete circuit ofthe data bus subscriber. In other words, the processing device 12receives data via the inputs 8 and 10 and transmits data via the outputs9 and 11. In addition, the processing device 12 may receive or outputdata from the inputs/outputs 13 and 14. In addition, the processing unit12 has access to a memory of the data bus subscriber 7 a, 7 b, . . . , 7n in which, for example, data, process data or instruction lists arestored.

The processing unit 12 may be designed to process received data and tooutput data. Data for processing may be received either from an upstreamdata bus subscriber or from inputs 13 of the data bus subscriber 7 a, 7b, . . . , 7 n. The inputs 13 of the data bus subscriber 7 a, 7 b, . . ., 7 n may in this case be connected to sensors 15 that for example sendmeasurement data, status data, and the like.

Processed data may be output either to a downstream data bus subscriberor to outputs 14 of the data bus subscriber 7 a, 7 b, . . . , 7 n. Theoutputs 14 of the data bus subscriber 7 a, 7 b, . . . , 7 n may beconnected to actuators 16, that for example carry out a certain actionusing the data directed to them. If data processing also takes place inthe upstream direction, data may also be received from a downstream databus subscriber 7 a, 7 b, . . . , 7 n and processed data may be sent toan upstream data bus subscriber 7 a, 7 b, . . . , 7 n.

For the sake of simplicity, the data bus subscribers 7 a, 7 b, . . . , 7n are only shown with one input 13 and one output 14 in the exemplaryembodiment shown here, and only data bus subscriber 7 b is connected toa sensor 15 and actuator 16. However, the skilled person understandsthat the data bus subscribers 7 a, 7 b, . . . , 7 n may have amultiplicity of inputs and outputs 13 and 14, and may be connected to amultiplicity of different sensors 15 and actuators 16. Thecharacteristic feature of the sensors 15 is that the sensors 15 receivedata or signals and send them to the data bus subscribers 7 a, 7 b, . .. , 7 n, while the actuators 16 receive data or signals from the databus subscribers 7 a, 7 b, . . . , 7 n and perform an action based onthese data or signals.

Alternatively, the interfaces 8, 9, 10 and 11 may be integrated in amodule unit and the data bus subscribers 7 a, 7 b, . . . , 7 n may beplugged into this module unit. The module units may also be described asbasic elements of the ring bus 6. The ring bus infrastructure is set upby the module units and the data bus subscribers 7 a, 7 b, . . . , 7 nare replaceable, so that the ring bus 6 may be set up with any arbitrarydata bus subscribers 7 a, 7 b, . . . , 7 n. The module units also serveto ensure that communication between the remaining data bus subscribers7 a, 7 b, . . . , 7 n is not interrupted even if a data bus subscriber 7a, 7 b, . . . , 7 n is removed, because communication takes place viathe remaining module units. The data bus subscribers 7 a, 7 b, . . . , 7n shown in this exemplary embodiment are often referred to as I/Omodules, due to their inputs and outputs 13, 14, which may be connectedto sensors 15 or actuators 16.

Although the data bus subscribers 7 a, 7 b, . . . , 7 n are shown asspatially separated from the sensors 15 or actuators 16 in the exemplaryembodiment shown here, the sensors 15 or actuators 16 may also beintegrated into the I/O module.

The ring bus 6 shown in this exemplary embodiment is based on cycleframe communication.

For example, a cycle frame may be defined as a recurring (cyclic),preferably equidistant, time interval in which data may be transferredon the ring bus 6. For example, the cycle frame has at least a startidentifier (SOC) and a time range for transmitting data. A plurality ofstart identifiers (SOC) of successive cycle frames are advantageouslyoffset equidistantly in time. The aforementioned time range is intendedfor transmitting the data packets that may be transmitted in the form ofdata packets within the cycle frame. The start identifier (SOC) and datapackets are transmitted via the ring bus 6 and pass through all data bussubscribers 7 a, 7 b, . . . , 7 n. Advantageously, the cycle frame isinitiated by the local bus master 3 in the ring bus 6. The startidentifier (SOC) is separate, i.e. may be transferred as an independentsymbol or may be advantageously contained in a start data packet (SOCpacket).

Zero, one or more data packets are transferred within the time range ofthe cycle frame. Advantageously, idle data is inserted in a cycle frame,in particular adjoining at least one data packet. Advantageously thetransmission of the data packets and/or the idle data causes anuninterrupted signal on the ring bus 6. The signal enables the data bussubscribers 7 a, 7 b, . . . , 7 n to temporally synchronize themselvesto the signal.

Advantageously, the cycle frame additionally has a trailer. The trailerhas a variable length and follows the time range for data transmission,preferably up to the next start identifier (SOC) of the next cycleframe. Advantageously, the trailer has idle data. Each data packet issent in a downstream direction from the local bus master 3 to the firstdata bus subscriber 7 a of the ring bus 6. This subscriber receives afirst part of the data packet via the interface 8.

Such a part of the data packet is also referred to below as a “piece” or“unit.” The data bus subscriber 7 a then carries out a processingoperation on the part, and then forwards the part to the next data bussubscriber 7 b via the interface 9; preferably at the same time, thefirst data bus subscriber 7 a receives a second part of the data packet,and so forth. The size of the parts of the data packet, i.e. thechunking of the data packet, depends on the receiving capacity of thedata bus subscribers 7 a, 7 b, . . . , 7 n; for example, a fixed numberof bits, for example 8 bits of the data packet, may be simultaneouslyavailable for processing at the data bus subscriber 7 a, 7 b, . . . , 7n.

Accordingly, the data packet passes through the data bus subscribers 7a, 7 b, . . . , 7 n in units, chunks or parts, for example in parts orsymbols of 8 bits. The part of the data packet that the last data bussubscriber has processed (in the exemplary embodiment shown here, databus subscriber 7 n), then passes through the ring bus 6 in the upstreamdirection, so that the parts starting from the last data bus subscriber7 n are again sent upstream in the direction of local bus master 3 byall data bus subscribers 7 a, 7 b, . . . , 7 n. For this purpose, thelast data bus subscriber 7 n either has a switchable bridge thatconnects interface 9 with interface 10 or a switchable bridge isconnected to the last data bus subscriber 7 n, which assumes thefunction of forwarding the parts of the data packet from the interface 9to the interface 10. Alternatively, the interface 10 of the data bussubscriber 7 n may also be connected directly to the interface 5 b ofthe local bus master 3 using a bypass line.

In the upstream direction, the units of the data packet or data packetsmay be looped back to the local bus master 3 by the individual data bussubscribers 7 a, 7 b, . . . , 7 n, as in the exemplary embodiment shownhere, without further processing. However, it is also conceivable thatin the upstream direction the units of the data packet are processedagain, so that the data packet may be processed twice, once in thedownstream direction to the last data bus subscriber 7 n and once in theupstream direction to the local bus master 3. For example, processingmay take place in the upstream direction by signal refreshing and/orphase shifting.

When processing the data packets in the downstream direction, i.e. awayfrom the local bus master 3, or in the upstream direction, i.e. towardthe local bus master 3, the processing is performed using instructionlists, and the instruction lists contain sets of instructions that theprocessing unit 12 of the data bus subscribers 7 a, 7 b, . . . , 7 n mayexecute. The instruction lists themselves may be sent to the individualdata bus subscribers 7 a, 7 b, . . . , 7 n an initialization phase bythe local bus master 3 or may advantageously be sent to the data bussubscribers 7 a, 7 b, . . . , 7 n during the ongoing communication, sothat the data bus subscribers 7 a, 7 b, . . . , 7 n are programmedwithout interrupting the communication.

An instruction list index may be used to communicate to the data bussubscribers 7 a, 7 b, . . . , 7 n which of the instruction lists thedata bus subscribers 7 a, 7 b, . . . , 7 n should use. This instructionlist index informs the data bus subscriber which stored instruction listit should use. An instruction list index is thus mapped to aninstruction list or vice versa, so that the instruction list index maybe used to identify the instruction list to use. For this purpose, theinstruction list index preferably has a value that is associated with aninstruction list; for example, the value indicates a specificinstruction list or its location in memory. For this purpose, the valueitself may be the memory address where the instruction list is stored,or where at least one first instruction of the instruction list isstored. Alternatively or additionally, the value may also refer to amemory area in which the corresponding instruction list is stored. Theterm “direct mapping” may also be used in the cases mentioned above. Thevalue of the instruction list index may also be used, for example, as anentry in a lookup table (LUT). The value of the instruction list indexis the input value of the lookup table. The output value of the lookuptable may be the memory address of the first instruction in theassociated instruction list or may otherwise identify the instructionlist. The lookup table may be stored as software or as hardware, in theform of for example logic circuits, and may indicate a bijective mappingfrom an input value to an output value, with the output value providingan indication of the instruction list to be used.

How a relationship is established between the instruction list index andthe instruction list is a function of the lookup table. The use of alookup table may also be referred to as “indirect mapping.” In the caseof direct and indirect mapping, however, the instruction list for thedata bus subscriber to use is bijectively identifiable, i.e. locatable,via the instruction list index. The instruction list index may beinserted into the data packet before the process data that will beprocessed, so that the data bus subscribers 7 a, 7 b, 7 n may use thecorresponding instruction list that corresponds to the sequence ofprocess data in the data packet. These instruction lists compriseinstructions that are adapted to the sequence of the process data in thedata packet. For example, the instruction lists may contain a “SKIP”instruction for process data that is not directed to the data bussubscriber 7 a, 7 b, . . . , 7 n, i.e. they may instruct the data bussubscriber 7 a, 7 b, . . . , 7 n to skip the corresponding part of thedata packet, while in contrast the instruction list for process datadirected to the data bus subscriber 7 a, 7 b, . . . , 7 n may comprisecorresponding instructions for processing the process data. Theprocessing of the process data may thus be decoupled from the actualposition of the process data in the data packet, because the instructionlists serve to adapt the data bus subscribers to the sequence of theprocess data in the data packet.

In the exemplary embodiment shown here, the local bus master 3 is usedfor converting between the higher-level bus 2, which may also bereferred to as a fieldbus, and the ring bus 6. The device responsiblefor the conversion in the local bus master 3 is shown in FIG. 2 .

FIG. 2 shows a block diagram of an exemplary embodiment of the deviceaccording to the invention, arranged in the local bus master 3. Thelocal bus master 3 is connected to the fieldbus 2 via the interface 4and is connected to the ring bus 6 via the interface 5. Accordingly, theinterface 4 may also be referred to as the fieldbus interface, and theinterface 5 may be referred to as the local bus interface.

For processing the data streams received or the data streams to be sentvia these interfaces, processing units may be connected to theinterfaces 4,5; in this case a first unit 17 that may also be referredto as a fieldbus core (FBC) may be connected to the fieldbus interface4, and a second unit 19 that may also be referred to as a local bus core(LBC) may be connected to the local bus interface 5.

The FBC 17 and LBC 19 are connected to a data management unit 18 via aparallel bus. The parallel bus may be a 32-bit parallel bus and may alsobe connected to a computing unit such as for example a microcontroller,μC or a processor capable of controlling the FBC 17, data managementunit 18, and LBC 19.

The data management unit 18 is adapted to transfer first symbols fromthe FBC 17 to the LBC 19 sequence-dependently, for example in unchangedsequence, so that they may be sent to the ring bus 6 via the local businterface 5, contained in at least one data packet. These first symbolsmay be process data received at the FBC 17 via the fieldbus 2 and viathe interface 4. The LBC 19 may be adapted to generate successive, localbus-compliant data packets for transmitting the process data on thelocal bus 6, and to insert the process data received from the datamanagement unit 18 into the corresponding data packet. The order of theprocess data may be retained, i.e. the process data in the data packeton the local bus may have the same sequence as the sequence in which theprocess data was received at the FBC 17 via the fieldbus interface 4. Inother words, fieldbus telegrams of the fieldbus 2 are received at theFBC 17 via the fieldbus interface 4, the fieldbus telegrams compriseprocess data in the form of first symbols with a fixed number of bits,for example 8 bits, i.e. 1 byte. These first symbols are arranged in thefieldbus telegram in a first sequence. The data management unit 18 isadapted to copy the process data from the FBC 17 to the LBC 19. The LBC19 is adapted to generate a data packet of the local bus 6, wherein thedata packet contains the first symbols of the process data in a secondsequence and wherein the first sequence and second sequence of thesymbols coincide.

The data bus subscribers 7 a, 7 b, . . . , 7 n are designed to evaluatethe process data in the data packet by means of instruction lists and aninstruction list index. For this purpose, the instruction list index,for example, is prepended to the process data in the data packet.Conversely, the data management unit 18 is adapted tosequence-dependently transfer second symbols from the LBC 19 to the FBC17, for example unchanged, so that they may be sent to the fieldbus 2via the fieldbus interface 4. These second symbols were received at theLBC 19 from the local bus 6 via the local bus interface 5. If the localbus 6 is a ring bus, then the local bus interface 5 is divided into twoparts, namely parts 5 a and 5 b, and data is transmitted downstream viapart 5 a to the local bus 6 and received upstream via part 5 b from thelocal bus 6.

The data management unit 18 also has a first and a second masterinterface 18 a and 18 b in the exemplary embodiment shown here. Thefirst master interface 18 a is connected to a slave interface 17 a ofthe FBC 17. In other words, the data management unit 18 and the FBC 17are in a master-slave relationship, in this case the control systemstarts from the data management unit 18. The data management unit 18thus reads data from the FBC 17 or writes data to the FBC 17 at a timethat the data management unit 18 predetermines. The second masterinterface 18 b of the data management unit 18 is connected to a slaveinterface 19 a of the LBC 19. The data management unit 18 and the LBC 19also have a master-slave relationship. Thus, the data management unit 18controls the transfer of data between the FBC 17 and the LBC 19, inparticular in both directions.

In addition, the data management unit 18 and the LBC 19 in the exemplaryembodiment shown here are connected via an additional line 25, andvalidity information may be exchanged between the data management unit18 and the LBC 19 regarding the transferred symbols via this additionalline 25. This validity information may then be used to delay thetransmission of the first and second symbols to the fieldbus 2 or localbus 6.

Advantageously, the connections between the units are designed as buses.A bus in this case may advantageously be a 32-bit parallel bus.Alternatively, the connection may be any other connection that allowsthe above-described data transfer between the units.

FIG. 3 a shows a schematic block diagram of an exemplary embodiment ofthe device according to the invention, implemented in a local bus master3 of a ring bus 6. In the exemplary embodiment shown here, the firstinterface 4 of the local bus master 3 receives a fieldbus telegram 20from the fieldbus 2. This fieldbus telegram 20, by way of example,contains 10 bytes, represented by square boxes, each box representing 1byte, i.e. 8 bits. Only the four black boxes, which correspond to 4bytes, contain the first process data 21. The other 6 bytes of thefieldbus telegram 20 are information corresponding to the bus protocolused on the fieldbus 2. However, these additional 6 bytes do not carryany process data 21 that is necessary for controlling or regulating theprocess; this additional information is only bus-specific information,such as for example addressing information, checksum information, andthe like. The first process data 21 are here also marked as [1], [2],[3] and [4], which symbolizes their sequence. The first process data 21are selected from the fieldbus telegram 20 by the FBC 17 and are storedfor example in a buffer. The selection may include the FBC 17transferring only the process data 21 in a buffer, but ignoring theadditional bytes of the fieldbus telegram 20.

In the exemplary embodiment shown here, the data management unit 18 hasa first data transfer unit 22 that reads the process data 21 from thebuffer of the FBC 17 via the master-slave interface connection 17 a, 18a and writes the process data 21 into a buffer of the LBC 19 via themaster-slave interface connection 18 b, 19 a. Thus, the first datatransfer unit 22 copies process data 21 from the FBC 17 to the LBC 19.The copying may be done according to instructions and the first datatransfer unit 22 may be adapted to prepend and/or append further data tothe process data 21 and/or interpolate it between the process data 21.Alternatively or additionally, the LBC 19 may be adapted to prependand/or append additional data to the process data 21 and/or interpolatethe additional data between the process data 21 and/or modify theprocess data 21.

For example, the additional data from the LBC 19 may be used to convertthe process data 21 into a local bus-compliant format, for example intoa data packet that may be sent to the local bus 6. In the exemplaryembodiment shown here, a symbol is respectively prepended and a symbolis respectively appended to the process data 21, to generate a datapacket 24 that carries the process data 21. The skilled personunderstands that although in this case only one symbol is prepended andappended to the process data 21, any arbitrary number of symbols mayalso be prepended and/or appended and that this depends solely on whichdata packet format is used on the local bus 6. The first data transferunit 22 may additionally be adapted to communicate the validity of theprocess data 21 to the LBC 19 after copying the process data 21 to theLBC 19. The validity may be communicated via the connection 25. Onlywhen the LBC 19 receives a signal that the copied process data 21 isvalid may the LBC 19 send this data downstream on the local bus 6 viathe local bus interface 5 a. The validity of the process data 21 isdetermined, for example, by a CRC or a valid bit.

The skilled person understands that parts of the data packet 24 that theLBC 19 generates may also be sent on the local bus 6 before receivingthe validity indication. In particular, if the parts of the data packet24 pass successively through the data bus subscribers 7 a, 7 b, . . . ,7 n as shown in FIG. 1 , the local bus master 3 at any given time sendsonly a part of the data packet 24, which the individual data bussubscribers 7 a, 7 b, . . . , 7 n then forward. In this case, the LBC 19may send the part of the data packet 24 containing the process data orother information on the local bus 6 before receiving the validityindication. In the exemplary embodiment shown here, the LBC 19 may sendthe appended symbol on the local bus 6 in advance, as the first part ofthe data packet 24.

The first data transfer unit 22 thus copies process data 21 from thefieldbus 2 to the local bus 6. During this copy process, the sequence[1], [2], [3], [4] of process data 21 is retained, i.e. the sequence ofthe process data 21 is the same in the fieldbus telegram 20 and in thedata packet 24 of the local bus 6. The process data 21 is copiedbus-neutrally, i.e. without the bus-specific information with which theprocess data 21 is received.

In the exemplary embodiment shown here, the two prepended symbols andthe four appended symbols of the fieldbus telegram 20 are not copied.

FIG. 3 b shows a schematic block diagram of an exemplary embodiment ofthe device according to the invention, implemented in a local bus master3 of a ring bus 6. In the exemplary embodiment shown here, the secondinterface 5 b of the local bus master 3 receives a data packet 26. Thedata packet 26, by way of example, contains 6 bytes, which arerepresented by square boxes, each box representing 1 byte, i.e. 8 bits.Only the four black boxes, which correspond to 4 bytes, contain thesecond process data 27. The other 2 bytes of the data packet 26 areinformation corresponding to the bus protocol used on the local bus 6.The second process data 27 are here also marked as [1′], [2′], [3′] and[4′], which symbolizes their order in the sequence. The second processdata 27 may be based on the first process data 21—as shown in FIG. 3 a—and may represent the process data 21 after it has passed through, i.e.been processed by, the local bus 6. The process data 27 is selected fromthe data packet 26 of the LBC 19 and for example stored in a buffer. Theselection may include the fact that the LBC 19 only transfers theprocess data 27 in a buffer, but ignores the additional bytes of thedata packet 26.

In the exemplary embodiment shown here, the data management unit 18comprises a second data transfer unit 23 that reads the process data 27from the buffer of the LBC 19 via the master-slave interface connection18 b, 19 a and then writes the process data 27 into a buffer of the FBC17 via the master-slave interface connection 17 a, 18 a. In other words,the second data transfer unit 23 copies process data 27 from the LBC 19to the FBC 17. The copying may be done according to instructions and thesecond data transfer unit 23 may be adapted to prepend and/or appendadditional data to the process data 27 and/or interpolate such databetween the process data 27.

Alternatively or additionally, the FBC 17 may be adapted to prependand/or append additional data to the process data 27 and/or interpolateit between the process data 27. For example, the additional data fromthe FBC 17 may be used to convert the process data 27 into afieldbus-compliant format, for example into a fieldbus telegram 28 ofthe fieldbus 2.

In the exemplary embodiment shown here, two symbols are prepended to theprocess data 27 and four symbols are appended, so as to generate afieldbus telegram 28 that carries the process data 27. The skilledperson understands that although in this case only a specific number ofsymbols are prepended and appended to the process data 27, this may alsobe any number of symbols; the number depends solely on the fieldbustelegram format used on the fieldbus 2. The second data transfer unit 23may additionally be adapted to copy only part of the process data 27 tothe FBC 17 and only to copy the remaining process data 27 afterreceiving a validity indication from the LBC 19 via the connection 25.As a result, the second data transfer unit 23 may control the time atwhich the FBC 17 sends the fieldbus telegram 28, because the fieldbustelegram 28 is always sent immediately when it has been completelyfilled with process data 27. If this is not yet the case, no fieldbustelegram 28 is yet sent. This allows a control system between the seconddata transfer unit 23 and the FBC 17 without any additional connectionbeing necessary. The validity of the process data 27 is determined basedon a CRC.

The components of the device according to the invention that have beendescribed as separate units, modules or interfaces in the describedexemplary embodiment may be implemented as separate hardware, but or maybe integrated onto the same semiconductor chip, and their function maybe implemented by a hardware arrangement of logic gates. For example,the units, modules, or interfaces may be implemented on an FPGA/ASIC.

The invention being thus described, it will be obvious that the same maybe varied in many ways. Such variations are not to be regarded as adeparture from the spirit and scope of the invention, and all suchmodifications as would be obvious to one skilled in the art are to beincluded within the scope of the following claims.

What is claimed is:
 1. A device for coupling a fieldbus to a local busfor connecting to a data bus subscriber, the device comprising: a fieldbus core connectable to the fieldbus and adapted to send and receivedata via the fieldbus; a local bus core connectable to the local bus andadapted to send and receive data via the local bus in at least one datapacket; and a data management unit connected to the field bus core andthe local bus core, the data management unit being adapted to transferfirst symbols from data received via the field bus core to the local buscore in a sequence-dependent manner such that the first symbols aretransferred to the local bus core in a same sequence in which thesymbols are received from the field bus core.
 2. The device according toclaim 1, wherein the data management unit is adapted to prepend and/orappend additional symbols to the first symbols.
 3. The device accordingto claim 1, wherein the data management unit is adapted to temporarilystore the first symbols.
 4. The device according to claim 1, wherein thelocal bus core is adapted to generate the local-bus compliant datapackets comprising the first symbols and to send the local-bus compliantdata packets on the local bus.
 5. The device according to claim 1,wherein the local bus core is adapted to receive the local-bus compliantdata packets from the local bus, and wherein the local-bus compliantdata packets contains second symbols.
 6. The device according to claim1, wherein the local bus core is additionally adapted to manipulate thefirst symbols.
 7. The device according to claim 4, wherein cycle timesof a cycle frame for the local-bus compliant data packets are adapted tothe cycle times of the fieldbus.
 8. The device according to claim 1,wherein the data management unit comprises a first master interface thatis connected to a slave interface of the field bus core, and/or whereinthe data management unit comprises a second master interface that isconnected to a slave interface of the local bus core.
 9. The deviceaccording to claim 8, wherein the data management unit comprises a firstdata transfer unit, and wherein the first data transfer unit is adaptedto read the first symbols from a buffer of the field bus core via thefirst master interface based on first instructions, and write thesesymbols into a buffer of the local bus core via the second masterinterface.
 10. The device according to claim 9, wherein the datamanagement unit is adapted to send the received first symbols to thelocal bus core via the second master interface using the first datatransfer unit when a validity of the received first symbols isindicated.
 11. The device according to claim 1, wherein the datamanagement unit comprises a second data transfer unit, and wherein thesecond data transfer unit is adapted to read second symbols from abuffer of the local bus core via the second master interface based onsecond instructions, and to write these symbols into a buffer of thefield bus core via the first master interface.
 12. The device accordingto claim 11, wherein the data management unit is adapted to write thesecond symbols into the buffer of the field bus core via the firstmaster interface using the second data transfer unit when a validity ofthe second symbols is indicated.
 13. The device according to claim 1,wherein the field bus core is adapted to check the validity of the datapackets received via the fieldbus, and the local bus core is adapted tocheck the validity of the local-bus compliant data packets received viathe local bus.
 14. The device according to claim 1, wherein the fieldbus core is adapted for serial sending and receiving of data via thefieldbus, wherein the local bus core is adapted for serial sending andreceiving of data via the local bus, wherein the data management unit isconnected to the field bus core via a parallel bus, and wherein the datamanagement unit is connected to the local bus core via a parallel bus.15. The device according to claim 1, wherein the field bus core is afirst logic circuit for communication with the fieldbus, wherein thelocal bus core is a second logic circuit for communication with thelocal bus, and wherein the first logic circuit and the second logiccircuit are adapted to perform computational operations independently ofone another.
 16. The device according to claim 1, the local bus corebeing adapted to generate and send local-bus compliant data packetsincluding the first symbols on the local bus.
 17. The device accordingto claim 1, wherein the symbols include process data.
 18. The deviceaccording to claim 1, wherein the field bus is a higher level bus thanthe local bus.
 19. A method for transferring data between a fieldbus anda local bus, wherein a data bus subscriber is connected to the localbus, the method comprising: receiving data at a first unit via thefieldbus, the received data having first symbols; and transferring thefirst symbols sequence-dependently into a second unit, such that thefirst symbols are transferred to the second unit in a same sequence inwhich the symbols are received from the first unit.
 20. A device forcoupling a fieldbus to a local bus for connecting to a data bussubscriber, the device comprising: a field bus core connectable to thefieldbus and adapted to send and receive data via the fieldbus; a localbus core connectable to the local bus and adapted to send and receivedata via the local bus in at least one data packet; and a datamanagement unit connected to the field bus core and the local bus core.